Session Start: Sun Sep 08 00:00:00 2013
Session Ident: #glitchpc
[00:00] * Now talking in #glitchpc
[00:00] * Topic is 'Welcome to #glitchpc chat. Profanity, trolls, and impersonation are not welcome here. Street1 has become a Silent Keyboard. http://www.legacy.com/obituaries/savannah/obituary.aspx?page=lifestory&pid=139870551'
Session Start: Sun Sep 08 00:15:15 2013
Session Ident: #glitchpc
[00:15] * Now talking in #glitchpc
[00:15] * Topic is 'Welcome to #glitchpc chat. Profanity, trolls, and impersonation are not welcome here. Street1 has become a Silent Keyboard. http://www.legacy.com/obituaries/savannah/obituary.aspx?page=lifestory&pid=139870551'
[00:15] * ChanServ sets mode: +a
[00:15] * ChanServ sets mode: +o ChanbotVII
[00:43] * BC_Programming (BC_Program@13DD81E6.53558F13.6889CB60.IP) Quit (Ping timeout)
[00:45] * MiniMoose (Mibbit@mib-B6BF8287.socal.res.rr.com) has joined #glitchpc
[00:46] * MiniMoose (Mibbit@mib-B6BF8287.socal.res.rr.com) Quit (Quit: http://www.mibbit.com ajax IRC Client)
[00:52] * Nat (nat@mib-921C62AC.socal.res.rr.com) Quit (Quit: zzzZZZzzzZZzzZZZzz)
[01:56] * BC_Programming (BC_Program@13DD81E6.53558F13.6889CB60.IP) has joined #glitchpc
[01:56] * ChanServ sets mode: +a
[01:56] * ChanServ sets mode: +o BC_Programming
[01:59] * PCdoc (PCdoc@DD2616A9.D82DAAE8.EE292452.IP) has left #glitchpc (Leaving)
[02:31] * Zuwer (Mibbit@mib-9196E61D.jetstream.xtra.co.nz) Quit (Ping timeout)
[02:40] * Zuwer (Mibbit@mib-9196E61D.jetstream.xtra.co.nz) has joined #glitchpc
[03:16]<@BC_Programming> hmm I think our VPN is a bit iffy
[03:17]<@BC_Programming> but at least i was able to file my work I did on Friday :D
[03:29] * PCdoc (PCdoc@DD2616A9.D82DAAE8.EE292452.IP) has joined #glitchpc
[03:54] * PCdoc (PCdoc@DD2616A9.D82DAAE8.EE292452.IP) has left #glitchpc (Leaving)
Session Start: Sun Sep 08 04:35:15 2013
Session Ident: #glitchpc
[04:35] * Now talking in #glitchpc
[04:35] * Topic is 'Welcome to #glitchpc chat. Profanity, trolls, and impersonation are not welcome here. Street1 has become a Silent Keyboard. http://www.legacy.com/obituaries/savannah/obituary.aspx?page=lifestory&pid=139870551'
[04:35] * ChanServ sets mode: +a
[04:35] * ChanServ sets mode: +o ChanbotVII
[05:48] * PCdoc (PCdoc@DD2616A9.D82DAAE8.EE292452.IP) has joined #glitchpc
[06:06] * FusRoDah (mulreay@mib-408AE6D.cable.virginmedia.com) has joined #glitchpc
[06:06] * ChanbotVII sets mode: +v FusRoDah
[06:06] * FusRoDah is now known as PixelsintheBlood
[06:06] * PixelsintheBlood is now known as Mulreay
[06:06] * ChanServ sets mode: +o Mulreay
[07:55] * dalem (dalem@B65D22F3.5B67314C.282D5A13.IP) has joined #glitchpc
[10:54] * PCdoc (PCdoc@DD2616A9.D82DAAE8.EE292452.IP) has left #glitchpc (Leaving)
[11:43] * Nat (nat@mib-921C62AC.socal.res.rr.com) has joined #glitchpc
[12:37] * NetworkWI-FI (Mibbit@mib-7B2DEDCF.skybroadband.com) has joined #glitchpc
[12:38] * NetworkWI-FI (Mibbit@mib-7B2DEDCF.skybroadband.com) has left #glitchpc
[13:16]<Immental1200> I've just found the worst space loss on a drive that I've ever seen I think
[13:16]<Immental1200> 120GB drive
[13:16]<Immental1200> But only 111 useable
[13:16]<Immental1200> That's nearly 10% missing
[13:22]<@BC_Programming> that's accurate
[13:22]<@BC_Programming> (120*1000*1000*1000)/1024/1024/1024=111.75
[13:31]<Immental1200> Hm
[13:31]<Immental1200> Most drives have more like 7%
[13:31]<Immental1200> Especially by 500's
[13:31]<Immental1200> my
[13:32]<@BC_Programming> 500GB = 465.66 GB Usable
[13:33]<Immental1200> I've got some with 470 / 475
[13:34]<@BC_Programming> probably not. if the 500GB is base 10 then you get 465GB usable
[13:35]<Immental1200> Jamer has one with 6% loss
[13:36]<jamer> but its only a 80 gig drive XD
[13:36]<@BC_Programming> 74.5GB Usable
[13:38]<jamer> yep
[13:38] * Nat (nat@mib-921C62AC.socal.res.rr.com) Quit (Connection reset by peer)
[13:39] * Nat (nat@mib-921C62AC.socal.res.rr.com) has joined #glitchpc
[13:43]<Immental1200> Anyone able to find graphics drivers for an HP 2133 for Windows 7 ;)
[13:43]<Immental1200> http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?cc=us&prodNameId=3687085&prodSeriesId=3687084&swLang=8&taskId=135&swEnvOID=1093#11360 only shows XP ones
[13:43]<Immental1200> Yet it shipped with Vista
[13:57]<jamer> http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3687085&prodTypeId=321957&prodSeriesId=3687084&swLang=13&swEnvOID=2096
[14:50]<@Mulreay> BC_Programming or camerongray or craig you around?
[14:50]<@Mulreay> Craig_remote that is
[14:50]<@BC_Programming> sup
[14:51]<@Mulreay> Hey need a quick question cleared up if you have a mo
[14:51]<@BC_Programming> ok
[14:53]<@Mulreay> I'm getting my GPU for the crossfire with the A8 tomorrow. The GPU I know has to be a HD6670 to work but there are two.. the 2gb has DDR3 and the 1gb has GDDR5.. if I use the 1gb would that not work properly as the system uses DDR3?
[14:54]<@BC_Programming> Graphics RAM is separate from your system RAM
[14:55]<@Mulreay> The system has onboard GPU or does that have no effect?
[14:55]<@BC_Programming> only the graphics card itself uses the Graphics RAM so what the motherboard has or supports doesn't come into play
[14:56]<@Mulreay> KK so out of these which one would you get? http://www.amazon.co.uk/Radeon-Graphics-PCI-Express-GDDR5-Dust-proof/dp/B004XANO24 or http://www.amazon.co.uk/Radeon-Graphics-Express-CrossFireX-Technology/dp/B0081LDY7Q/ref=sr_1_61?m=A3P5ROKL5A1OLE&s=computers&ie=UTF8&qid=1378320583&sr=1-61
[14:58]<@BC_Programming> I'd go with the 1GB, Faster Memory is better than More but slower memory, especially GDDR5 versus GDDR3
[14:58]<@Mulreay> K thanks bud
[14:58]<@BC_Programming> may want to wait for cam/craig/calum to weigh in on that if they pop in
[14:58]<@Mulreay> yeah will do
[14:58]<Immental1200> I'd agree
[14:58]<Immental1200> Although
[14:59]<Immental1200> Personally, I'd not crossfire with an A8
[14:59]<Immental1200> THe issues you get with SLI and crossfire are ridiculous
[14:59]<Immental1200> And that's with identical cards
[15:00]<Immental1200> Plus, if you're gaming... some games crap out with crossfire
[15:00]<Immental1200> And perform much better with one card
[15:00]<@BC_Programming> considering you didn't even know how megabytes translate to mibibytes I think we'll put that advice in arrears
[15:01]<Immental1200> 8 bits = 1 byte
[15:01]<@BC_Programming> megabytes to mibibytes, not bits to bytes
[15:01]<Immental1200> I've never heard the term mibibytes
[15:03]<@BC_Programming> megabyte= 1000 kilobytes. Mibibyte = 1024 kibibytes
[15:03]<@BC_Programming> the standard metric is often used but with the binary prefix definition.
[15:04]<Immental1200> Wait...
[15:04]<Immental1200> I thought
[15:04]<Immental1200> 1,000 was used by HDD makers
[15:04]<Immental1200> And 1,024 was the standard
[15:04]<Immental1200> So 1,000 mibityes = 1,024 megabytes
[15:05]<Immental1200> Ignore that last bit
[15:05]<Immental1200> But yeah... 1024 is what's used
[15:05]<Immental1200> And HDD makers just do it differently?
[15:06]<@BC_Programming> HDD manufacturers were the only ones using the Metric prefixes properly to begin with, though they did it for their own gain
[15:07]<Immental1200> Hm
[15:07]<Immental1200> I was always told it was the other way round xD
[15:08]<@BC_Programming> the metric system is base 10. Kilo, Mega, etc. are ALWAYS base 10 by definition
[15:08]<@BC_Programming> a Kilometer is 1000 meters. a Kilobyte is (technically) 1000 bytes
[15:08]<Immental1200> Interesting
[15:09]<Immental1200> Should I attempt to correct my systems hardware teacher ;)
[15:09]<@BC_Programming> No, I use the old definition because it's ironically less confusing at this point
[15:10]<@BC_Programming> the confusion is because Memory is only present in powers of two simply because of how it works... and they needed to measure it in some convenient way, so they used a base-2 system oriented around metric prefixes
[15:10]<Immental1200> You lost me
[15:10]<Immental1200> It's probably easier if you don't explain XD
[15:11]<@BC_Programming> A chip could be 1024 bytes
[15:11]<@BC_Programming> but no chip could be made with 1000 bytes
[15:11]<Immental1200> Because 1, 2, 4, 8, etc?
[15:12]<@BC_Programming> because memory is addressed in binary
[15:12]<Immental1200> So it has to be in 2's?
[15:12]<@BC_Programming> pretty much
[15:12]<Immental1200> Something I got asked at an interview a month ago
[15:13]<Immental1200> That neither me or the guy asking questions was totally sure about
[15:13]<Immental1200> Is, simply, what's the difference between 32 and 64 bit when you're on about the CPU itself.
[15:13]<Immental1200> Is it double the 'bandwidth'?
[15:13]<@BC_Programming> wow
[15:14]<Immental1200> Why wow
[15:14]<Immental1200> The guy was just trying to see what I knew, the company was all cloud based stuff + windows server / azure, not hardware or programming or anything like that
[15:14]<@BC_Programming> So that justifies them not understanding basics of the hardware
[15:15]<Immental1200> Eh
[15:15]<Immental1200> He has someone who specifically deals with hardware, he was the boss, why does he need to know xD
[15:15]<Immental1200> Is probably the corporate logic there
[18:56]<Craig_remote> Hey Mulreay,BC_Programming, camerongray, and so on...
[18:57]<@BC_Programming> hey Craig
[18:57]<Craig_remote> How goes it BC?
[18:57]<jamer> you forgot me ...
[18:57]<jamer> :P
[18:57]<Craig_remote> I said and so on
[18:58]<jamer> i remember you used to call me by another name
[18:58]<Craig_remote> John
[18:58]<Craig_remote> :P
[18:58] * Craig_remote is now known as Craig
[19:04]<jamer> :P
[20:25] * Zuwer (Mibbit@mib-9196E61D.jetstream.xtra.co.nz) Quit (Quit: http://www.mibbit.com ajax IRC Client)
[20:28] * Zuwer (Mibbit@mib-9196E61D.jetstream.xtra.co.nz) has joined #glitchpc
[20:35] * Erika (nds@mib-735470C7.lightspeed.wepbfl.sbcglobal.net) has joined #glitchpc
[21:04] * Zuwer (Mibbit@mib-9196E61D.jetstream.xtra.co.nz) Quit (Quit: http://www.mibbit.com ajax IRC Client)
[22:28] * Tux2 (Tux2@mib-58B6CB9.hlrn.qwest.net) has joined #glitchpc
[22:28]<Tux2> and it's BC_Programming!
[22:28] * ChanbotVII sets mode: +v Tux2
[22:29]<@BC_Programming> hi
[22:48]<Erika> hi
[23:48] * KindOne (KindOne@ED1F53AE.736D2691.90984A5.IP) Quit (Ping timeout)
[23:52] * KindOne (KindOne@87320E72.C8CD50A.90984A5.IP) has joined #glitchpc
[23:55] * Nat (nat@mib-921C62AC.socal.res.rr.com) Quit (Quit: I used to have good quit messages. Those days have been long gone. :()